Skip to main content

Folder and Database Organization

Folder Structure​

What is required for each run​

Each run has multiple steps. To make one run we will have to do the following:

  1. Generate Multiple Plumes
  2. Generate Multiple Rainfall Files
  3. Generate Multiple INP Files
  4. Generate Multiple signal Files
  5. Combine the Signal Files
  6. Run Optimization

We will need a nested folder structure and at least at first we will need to keep copies of all files. The EPA has to be able to trace back to see the process as much as possible.

A single Chama Optimization run is made of Multiple Signal File Runs.

A signal File is made by a single SWMM Run. The SWMM run will be made with a single Plume and Rainfall combination. The Plume will become part of the INP file where the rainfall will be placed in the same file as the inp file and called rainfall.dat This way the SWMM engine will run the correct rainfall.

So a run folder be named as follows. Auto Incrementing RunID. and Auto incrementing Signal File. There will be many Signal folders within the single Run Folder.

In the single Run folders there will need to be the following:

  1. INP File (Modified for the Plume)
  2. Rainfall.dat File
  3. After SWMM is run there will be a signal file generated.

After all individual Signal Files have been generated then a combined signal folder with the combined signal file will be created. Using the modified combined signal file(current script only can combine 2 signal files)

This will be the signal file that is run in Chama OPT. There are also other files needed to run Chama OPT This would be a good place to put them as well. They will need to be generated right now they are hand crafted.

  1. Scenario files
  2. Potential Sensor Locations

Static Sections​

To create the INP files we will need to create plumes and Rainfall files there should be a separate section

Folder Structure Images Top Down​

FS Level 1 FS Level 2_1 FS Level 2_2 FS Level 2_3 FS Level 3_1 FS Level 4_1 FS Level 4_2 FS Level 4_3 FS Level 3_2 FS Level 4_4 FS Level 4_5

Database Structure​

Table Definitions​

  1. Base INP - Similar to the TPL File in Ostrich it is the base file that contains the sections of the INP file that will not change. (This will reference an INP file.)
  2. Potential Sensor Locations - Potential sensor Locations are required for 2 reasons.
    1. It is a required file in chama
    2. It is used to reduce the number of signals in the signal files. Banklick for example has 351 subcatchments.
  3. Chama Scenario - This is a required file for chama.
  4. Rainfall - This is the rainfall Data. There will be multiple rainfall files.
  5. Plume - This is the other half of the INP file it will contain sections for Loadings and Possibly pollutants. It will be based on however we set up the plumes.
  6. Signals - This table will contain the ID's that go into each signal file. An Inherited Run ID and Location for the signal file.
  7. Runs - This will contain a run Id, Potential Sensor Locations ID, Chama Scenario, and a combined Signal File location.
  8. Results - This will contain the Inherited Run ID and the File Location with the results files. Depending on the results we may also want summary and or detailed results placed here as well.

Possible Database ERD​

This is a mock up DB3 that was then put into Valentina to generate a Quick and dirty ERD. This was the fastest way I could think of doing this.

Mock Chama ERD